One page. The writing, the work, and the argument about both.

Margin is six things that only make sense together. Here is each of them, and the specific job it takes off your plate.

Docs people actually finish.

A fast, plain editor that gets out of the way, with every source the page depends on hanging in its margin. Nothing is pasted in and left to rot — the Slack thread, the pull requests and the roadmap item stay linked to the paragraph that cites them.

Start a doc
  • #launch in Slack
  • 12 PRs in GitHub
  • Q3 roadmap in Linear
  • Support tickets

Q3 launch brief

Everything that has to be true before the 14th, and who owns it.

The note is the unit of work.

Select any line and leave a note in the margin. It carries the paragraph it sits beside, so whoever picks it up already has the context — and it closes when the work lands, not when someone remembers to tick it.

See how notes travel
This paragraph is doing two jobs. Split it. Priya

Usage pricing means a team of forty pays for what forty people actually did, not for forty seats. It is the only model that does not punish you for inviting the person who needed to read it.

Agents that read before they write.

An agent reads the note, reads the page and reads the ten pages that page links to. Then it does the work and shows you every step it took, so you are reviewing a draft rather than trusting a black box.

Read the agent guide

Support agent

Done

Answered 14 tickets from the runbook. Three needed a person — they are in your inbox with the context attached.

Ran at 06:40, before anyone was up

Every open note on one board.

Notes become cards the moment somebody needs them done, and the card and the note are the same object — move it, assign it, close it, and the paragraph it came from updates with it.

See a board

To do

  • Rewrite pricing headline
  • Security review

Doing

  • Ship the margin rail
  • Draft the 2.4 changelog

Done

  • Migrate the old notes

Connected to where the work already is.

Slack threads become notes, pull requests close them, Linear issues stay in step and support tickets find the runbook by themselves. Margin does not ask your team to move — it asks them to write things down once.

Browse connections
  • Slack Threads become notes Connected
  • GitHub PRs close their notes Connected
  • Linear Issues sync both ways Connected
  • Figma Frames embed live Connected
  • Zendesk Tickets find the runbook Add

Six things you stop doing yourself.

Not features. The specific jobs a team hands over in the first fortnight.

  • Triage the inbox

    Every message read, sorted and answered where the answer is already written down.

  • Write the changelog

    From the pull requests that actually shipped, in the voice the last ten entries used.

  • Keep the docs honest

    Flags the page that contradicts the one you just changed, before a customer finds it.

  • Answer the same question

    The eleventh time somebody asks where the runbook is, it answers instead of you.

  • Chase the sign-off

    Knows who owns the decision, asks them once, and closes the note when they reply.

  • Summarise the week

    One page on Friday: what moved, what slipped, and the note nobody picked up.

Try it on the doc you are avoiding.

Open Margin, paste the thing nobody has finished, and leave one note in its margin.

Start free Book a demo